|
In software engineering, schema migration (also database migration, database change management〔http://www.liquibase.org/ Liquibase Database Refactoring〕〔http://flywaydb.org/ Flyway: The agile database migration framework for Java〕) refers to the management of incremental, reversible changes to relational database schemas. A schema migration is performed on a database whenever it is necessary to update or revert that database's schema to some newer or older version. Migrations are performed programmatically by using a ''schema migration tool''. When invoked with a specified desired schema version, the tool automates the successive application or reversal of an appropriate sequence of schema changes until it is brought to the desired state. Most schema migration tools aim to minimise the impact of schema changes on any existing data in the database. Despite this, preservation of data in general is not guaranteed because schema changes such as the deletion of a database column can destroy data (i.e. all values stored under that column for all rows in that table are deleted). Instead, the tools help to preserve the meaning of the data or to reorganize existing data to meet new requirements. Since meaning of the data often cannot be encoded, the configuration of the tools usually needs manual intervention. == Risks and Benefits == Schema migration allows to fix mistakes and adapt the data as requirements change. They are an essential part of software evolution, especially in agile environments (see below). Applying a schema migration to a production database is always a risk. Development and test databases tend to be smaller and cleaner. The data in them is better understood or, if everything else fails, the amount of data is small enough for a human to process. Production databases are usually huge, old and full of surprises. The surprises can come from many sources: * Corrupt data that was written by old versions of the software and not cleaned properly * Implied dependencies in the data which no one knows about anymore * People directly changing the database without using the designated tools * Bugs in the schema migration tools * Mistakes in assumptions how data should be migrated For these reasons, the migration process needs a high level of discipline, thorough testing and a sound backup strategy. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「schema migration」の詳細全文を読む スポンサード リンク
|